feat(node): Add Crons monitoring for BullMQ job schedulers - #25472

Part of a series adding automatic Crons monitoring for the most-used job schedulers in each SDK. Check-ins for a monitor that doesn't exist yet are dropped, so today each monitor has to be created by hand with its schedule copied from the code. Sending the job's schedule as the monitor config lets Sentry create the monitor and keep it in sync.

This adds Sentry.cron.instrumentBullMQWorker, next to the existing cron, node-cron and node-schedule helpers. It listens to the worker's events instead of wrapping the processor, so sandboxed processors work too. Each job from a job scheduler sends check-ins under the scheduler id, with its pattern (in tz, or the server's time zone) or every as the monitor config.

const worker = new Worker('reports', processor, { connection });
Sentry.cron.instrumentBullMQWorker(worker, {
  excludeJobSchedulers: ['cache-warmup', /^tmp-/],
});

Schedules Crons can't express, like sub-minute intervals or ?/W syntax, and schedulers with limit or endDate check in without a config. Legacy repeatable jobs (queue.add with repeat) aren't monitored.

pnpm-workspace.yaml adds msgpackr-extract to allowBuilds, which bullmq needs for the integration tests.

Docs: getsentry/sentry-docs#20053